SPEC-PWF-INC · v0.2
2 July 2026
Owner: Platform team

1Trigger, outcome & lanes

What starts this process, where it ends, who acts and on which surfaces.

Where the customer reads the incident. An alarm's cause → effect is read on the device-detail multi-metric telemetry stack (PTL-1, SPEC-UIX-DEV §7.1): the excursion shows on the relevant pane and the incident instant is dropped as an event-milestone annotation across the whole stack. A door-open incident is one such trigger — the enclosure's front · back · side doors each run as an open→close band on the stack's door-access pane and escalate to alarm past the 5-minute threshold — before the customer acknowledges or opens a ticket. This is presentation of the same Alert the flow below drives; no new step or event.

2The flow

Top to bottom in sequence; lanes are the actors. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions.

3Steps

Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.

4Related documentation

Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.

5Rules in play

The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.

6Revision history

Version	Date	Changes
0.1	13 Jun 2026	First draft — composed with the workflow set (SPEC-PWF v0.1).
0.2	2 Jul 2026	Incident surface note (§1). Recorded that the customer reads an alarm's cause → effect on the device-detail multi-metric telemetry stack and that a door-open incident (front · back · side, alarm past 5 min) surfaces on its door-access pane + as a cross-stack annotation (PTL-1, SPEC-UIX-DEV §7.1). Presentation alignment only — no step, lane or event change; the Alert lifecycle is unchanged.